-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Numpydoc Compliance #1988
Numpydoc Compliance #1988
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! Following my comments you might want or not to change conventions, I can check again later
Co-authored-by: Pascal Bourgault <[email protected]> Co-authored-by: Éric Dupuis <[email protected]>
for more information, see https://pre-commit.ci
Co-authored-by: Pascal Bourgault <[email protected]>
Note It appears that this Pull Request modifies the On inspection, the No further action is required. |
@coxipi I just want to update the CHANGELOG one last time, but otherwise, this PR is simply waiting on the fix to support the latest Thanks again for your comments! |
Pull Request Checklist:
number
) and pull request (:pull:number
) has been addedWhat kind of change does this PR introduce?
numpydoc
library for docstring validation.codespell
configuration (previously was not parsing all relevant files).\*
to use*
instead.flake8
'sRST210
andRST213
checks that were flagging*
symbols in docstrings as unterminated emphasis and strong tags.Indictor.parse_indice
that sanitizes the*
symbols fromParameters
entries.numpydoc
specification.Does this PR introduce a breaking change?
It should not. Call signatures and docstrings will be slightly changed.
Other information:
https://numpydoc.readthedocs.io/en/latest/validation.html
Except for the custom fields that we use to populate our documentation, the docstrings of
xclim
are very consistent and virtually compliant with the standard now.Both
xclim.sdba
andxclim.core.missing
are not evaluated bynumpydoc
due to major refactoring efforts that are underway (https://github.com/Ouranosinc/xsdba) or needed (#2000).